##[group]The deploy tool's tests
npm run test:deploy
##[endgroup]
shell: bash -e /home/runner/_temp/18dfa98e3c8629f3.sh

> test:deploy
> node --test "scripts/deploy/*.test.mjs"

error: no matching package named `base64` found
location searched: crates.io index
required by package `g1t-api v0.1.0 (/home/runner/work/repo/apps/api)`
note: offline mode (via `--offline`) can sometimes cause surprising resolution failures
help: if this error is too confusing you may wish to retry without `--offline`
✔ the manifest matches every wrangler config in the repository (94.597799ms)
✔ every wrangler.jsonc is found, and only checked-in ones (77.606646ms)
✔ problems are found: an unlisted config, a later-stage binding, a wrong database, an unnamed KV (88.324255ms)
✔ stages follow bindings: nothing binds to a unit that ships after it (1.622269ms)
✔ Rust workers build with the shared script and the same wasm-opt level (1.455938ms)
✔ shared crates and packages are read from workspace metadata (1.818328ms)
✔ the runner's image is built from the runner crate and what it uses, on the base its lock names (0.82531ms)
✔ services/runner/base.json records the base its folder builds (16.697825ms)
✔ an image's hash ignores line endings, and its tags say what they are (302.947181ms)
✔ only the lockfile entries the runner is built from name its image (1.346359ms)
✔ the runner's deploy config names its image by reference, beside its wrangler.jsonc (80.891833ms)
✔ the registry is asked for an image's manifest, without Docker (2.895387ms)
✔ a push counts only when it ends with a digest, and is tried again (1.595379ms)
✔ a static Linux binary is told from a dynamic one (1.414248ms)
﹣ path dependencies agree with Cargo's own resolved graph (4425.901339ms) # cargo metadata could not resolve offline
✔ every import that leaves a unit's folder is covered by its dependencies or inputs (270.556832ms)
✔ a shared crate's change reaches every unit built from it, and no other (2.099288ms)
✔ a shared package's change reaches what imports it (0.37053ms)
✔ own folders, declared inputs and root files (1.270048ms)
✔ a Cargo.lock change reaches only crates that use what changed (0.7342ms)
✔ a package-lock change reaches through workspace links (1.02724ms)
✔ decide: changed units deploy, others wait, unknown ones deploy (1.204739ms)
✔ decide: --force deploys unchanged units; a commit missing from history deploys (0.33899ms)
✔ decide: Cargo.lock counts only where it reaches (1.234489ms)
✔ decide: the runner's image rebuilds only when what it is built from changed (0.327039ms)
✔ the plan as data: migrations, and each stage's units in jobs that share a build (2.182438ms)
✔ units are picked by short name, folder or Worker name (0.866319ms)
✔ a CI job installs only what its units need (1.828118ms)
✔ a deploy is annotated with its commit, and read back (2.175178ms)
✔ the live commit: the live version's, looking through secret changes (2.050498ms)
✔ Wrangler's output: pending migrations and the version a deploy made (1.248199ms)
✔ the pool runs everything, no more than its limit at once (197.386042ms)
✔ self-hosting builds every Rust service the manifest says it runs (2.274697ms)
✔ docs/SELF_HOSTING.md's table names every unit (0.73468ms)
✔ resolveStack works on a manifest with no workspace crates or packages (6.520263ms)
✔ decide: a commit older than what runs is never deployed by accident, even forced; --rollback means it (0.71651ms)
✔ a deploy by hand reports to the repository on g1t, and a workflow's does not (5.083956ms)
scheduler: g1t-webhooks (* * * * *) is still running from the last time; skipped
scheduler: g1t-webhooks (* * * * *): 200 {"outcome":"exception"}
✔ fields read numbers, ranges, lists and steps (5.090885ms)
✔ the services' crons match when hosted g1t's would fire (5.595425ms)
✔ what is due is each matching cron of each service (1.518339ms)
✔ a run asks Wrangler for the handler, and a slow one is not doubled (202.774696ms)
✔ a deploy is announced to status.g1t.sh with the token, and without one nothing is sent (223.241927ms)
✔ an announcement that fails is a warning, never a failed deploy (4.177486ms)
✔ the stages run inside the window: started before, finished after, even when they throw; a dry run says nothing (5.302125ms)
✔ deploy.mjs announces every deploy, and the workflow passes it the token (2.075188ms)
ℹ tests 45
ℹ suites 0
ℹ pass 44
ℹ fail 0
ℹ cancelled 0
ℹ skipped 1
ℹ todo 0
ℹ duration_ms 7395.245307
